Package-level declarations
Types
Storage-agnostic DecaySweeper over a PropositionRepository, plus an optional hook to materialise decayed confidence where a backend can cache it.
Configuration for a DecaySweeper run.
Evaluates propositions for lifecycle transitions and applies them according to a StatusTransitionPolicy.
Result of a DecaySweeper run.
Represents something derived from sources with associated uncertainty.
A reference to an entity within a proposition.
Decorator that emits a ProjectionBatchCompleted event after every projectAll call.
Decorator that emits lifecycle events at the persistence boundary.
Opt-in capability for querying the entity-relationship axis of the knowledge graph: neighbourhoods, paths between entities, and the provenance lineage behind a single proposition.
Opt-in capability for navigating the proposition abstraction hierarchy — finding source propositions and the abstractions derived from them.
Utility class to track the mapping from mentions to their SuggestedEntity representations. Used internally to coordinate between extraction and resolution.
The role an entity mention plays in a proposition.
Marker interface for types derived from propositions (graph relationships, Prolog facts, etc.). Carries confidence, decay, and grounding inherited from Derivation, plus a link back to the source propositions.
Proposition couldn't be projected due to an error or incompatibility.
Why a proposition could not be projected (or was skipped). Use describe for a human-readable summary, or branch on the concrete subtype to react programmatically without parsing text.
The outcome of attempting to project a single proposition.
Aggregated results from projecting multiple propositions.
Proposition was skipped because it didn't meet projection criteria.
Proposition was successfully projected.
Transforms propositions into a typed target representation (graph, Prolog, memory context, etc.).
A proposition is a natural language statement with typed entity mentions. Propositions are the system of record - all other representations (Neo4j relationships, Prolog facts, vector embeddings) derive from them.
Extracts propositions from text chunks. This is the entry point for the proposition-based ingestion pipeline.
What a batch of propositions actually landed on: which stored proposition each one you handed in became.
Composable query specification for propositions.
The full proposition repository: combines the base persistence port with every opt-in capability (vector similarity, abstraction-hierarchy traversal, temporal queries) and bridges to the RAG search contract via CoreSearchOperations.
The lifecycle status of a proposition.
Base persistence port for propositions: CRUD, identity lookups, and the composable query.
Portable boundary that lets domain code program against a PropositionStore and reach for the optional vector and graph capabilities without first knowing whether the backing store honours them.
Which backend provides a PropositionRepository, for selecting/flipping implementations.
The three source-revision finders answered by reading the context and filtering loaded provenance in memory.
The event-emitting decorator, over a delegate that can subtract provenance atomically.
Opt-in capability for taking named evidence off a proposition in one atomic step.
Common interface for anything that references entities via mentions. Propositions, projected relationships, and other constructs can implement this to provide consistent entity access.
Relationship types for DICE graph schema.
The event-emitting decorator, over a delegate that answers both source-revision queries and provenance subtraction.
Opt-in capability for asking which propositions were read from a source, and from which revision of that source.
A mention suggested by the LLM during proposition extraction. Lighter weight than EntityMention - contains only what the LLM provides.
A proposition suggested by the LLM from chunk analysis. This is the output type from the propose_facts prompt.
Container for propositions suggested from a single chunk.
Open carrier for an LLM- or extractor-emitted hint that something should be persisted. Concrete subtypes decide what — entities (com.embabel.dice.common.SuggestedEntity), propositions (SuggestedProposition), or app-domain facts shipped by downstream modules (e.g. SuggestedBiller).
Handler for one concrete Suggestion subtype. Multiple handlers may register for the same type — for example a SuggestedBiller could be processed by both an entity-promoter (writing the Org to the KG) and a biller-index writer.
Opt-in capability for time-window and effective-confidence queries over propositions.
Opt-in capability for proposition stores that support vector similarity search and clustering.